|
•
|
|
•
|
Important: For more information on IPCF function and supported interfaces, refer Cisco ASR 5000 Series Intelligent Policy Control Function Administration Guide.SSC provides a centralized and simplified policy management for the network. It interfaces with IPCF over Sp interface which is based on standard Sh protocol, for subscriber profile and usage related transactions. SSC also supports a proprietary interface to receive event notification data from IPCF.
Important: For more information on SSC function and supported interfaces, refer Cisco ASR 5000 Subscriber Service Controller Installation and Administration Guide.|
•
|
|
•
|
|
•
|
Important: PPT is a policy provisioning tool. It does not perform any functions related to subscriber profile provisioning, such as creating subscribers or associating data plans to subscribers. Such functions are performed by the SSC component of the PCC solution. 
|
•
|
|
•
|
Apache Web Server: Apache server is used to relay requests received from clients to the PPT server.
PostgreSQL Database: PostgreSQL RDBMS provides centralized database for most of the data being accessed by different components of PPT. It stores details of users accessing PPT application. Along with user details, it also stores information pertaining to elements such as IPCF and SSC nodes, audit logs of traffic types, rules and rule bases, Access Point Names (APNs), user defined conditions and actions along with configured policies.
PSMon: This is a script which runs as a daemon process on PPT server. It monitors the server components including Apache server, PostgreSQL, and Policy Provisioning Server. PSMon periodically examines state of PPT components and restarts the in-active components. The administrator can configure a PSMon configuration file that contains a list of components to be monitored along with the time interval after which their state should be examined, and maximum number of retries for restarting a component.
Important: The PSMon configuration file psmon.conf is located in <ppt_install_dir>/3rdparty/psmon directory.Notification server: This is a script which is responsible for generating SNMP v1 or v2 traps including the instances whenever a PPT component is started, stopped or restarted. It also sends traps for events related to Web server, Database and PSMon. The SNMP targets can be configured using the script confSNMPTarget.sh located in <ppt_install_dir>/scripts directory. PPT administrator can configure a maximum of 5 SNMP targets at a time, and for each target can specify whether it should receive SNMP v1 or v2 traps or do not receive any traps at all.
Important: Notification server checks for the Notification target file after every five minutes, hence changes made to the SNMP target configuration file would not take more than five minutes to come to effect.Scheduler: Scheduler is a background process that synchronizes PPT data base with IPCF, SSC and PCEF instances that are configured in PPT application. The synchronization process gets executed during various scenarios such as addition or deletion of IPCF/SSC/PCEF instance to the PPT application, or when any of the configured IPCF/SSC/PCEF instance becomes active, or when synchronization is requested by the PPT administrator using GUI. Synchronization can be scheduled using parameters from the <ppt_install_dir>/etc/ppt.cfg file.
Monitor Server: Monitor server is a background process. It stores the status of all the IPCF, SSC and PCEF instances that are configured in the PPT application. Any such instance can be either manageable or not-manageable, this information is stored in a PPT database. Monitor server process, does not allow PPT application to select an un-manageable IPCF/SSC/PCEF instance as a primary or active resource in the deployment.
Browser: This is the only component required at the client side. It is an Internet browser, which requires the Java script and cookies enabled.
RHEL Operating System Cisco MITG RHEL v5.5 OS is a custom image that contains software packages that are mandatory to support Cisco MITG external software applications. Users must not install any other applications on the platforms running Cisco MITG RHEL v5.5 OS. For detailed software compatibility information, refer Cisco MITG RHEL v5.5 OS Application Note.
Important: Solaris 10 must be installed using the End User System support 64-bit software group and it must be specified during the installation of the operating system. This option installs the libraries required for proper operation of the PPT.
Important: Solaris 10 Kernel patch beyond 137137-09 may result in kernel panic while executing or invoking system calls.
Important: In some deployments server components of PPT and Web Element Manager (WEM) applications may share a common hardware platform. 
|
•
|
XML-HTPPs: PPT is a client-server application. A browser based policy configuration interface is used to access the data stored on the PPT server. The secure HTTP interface is used by the browser based GUI of PPT to communicate the information with PPT server.
|
|
•
|
XML-RPC: PPT requires objects such as data or service plans, subscription tiers, notification templates and subscriber profile attributes, to configure and maintain policies. The XML-RPC interface is used to fetch such objects from appropriate Subscriber Service Controller (SSC) instances.
|
|
•
|
CORBA: PPT requires objects such as Quality of Service (QoS), Policy Charging and Control service, data service as well as time definitions, to configure and maintain policies. CORBA interface is used to fetch these parameters from appropriate instance of Intelligent Policy Control Function (IPCF). The CORBA interface can also be used to fetch objects such as rule definitions, rule bases and APN information from the PCEF, for configuring and maintaining policies.
|
